Skip to content
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.

Faq #517

Merged
merged 2 commits into from
Feb 24, 2017
Merged

Faq #517

merged 2 commits into from
Feb 24, 2017

Conversation

Dieterbe
Copy link
Contributor

@Dieterbe Dieterbe commented Feb 3, 2017

No description provided.

docs/faq.md Outdated
Furthermore, we have optimizations for this use case:

* Index filtering: when you request data, we exclude items from the result set that have not been updated in 24hours before the "from" of the request (as the data will be all null anyway)
* Index pruning: if enabled, we delete series from the index if no data has been received in "max-stale". (but keep data until it expires, in case the same metric gets re-added). This is useful beecause the query editor does not send a time range. Note that this setting is applied to *all* metrics.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

beecause double e.
also: I'd say "max-stale" time just because it sounds a little more intuitive

docs/faq.md Outdated

* Index filtering: when you request data, we exclude items from the result set that have not been updated in 24hours before the "from" of the request (as the data will be all null anyway)
* Index pruning: if enabled, we delete series from the index if no data has been received in "max-stale". (but keep data until it expires, in case the same metric gets re-added). This is useful beecause the query editor does not send a time range. Note that this setting is applied to *all* metrics.
* GC: removes metrics from metrictanks' ringbuffer if they become stale (see `metric-max-stale`), which means data will most likely come from cassandra or possibly in memory chunk-cache, but does not affect the index.
Copy link
Contributor

@replay replay Feb 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not completely sure, but shouldn't it be metrictank's instead of metrictanks'?
or possibly the in memory chunk-cache i think there's a the missing


Metrictank aims to provide a proper implementation of [metrics 2.0](http://metrics20.org/)
(it helps that both projects share the same main author)
As such, metrics can have tags and they are indexed as such. However we don't expose this yet through the search or query interface,
Copy link
Contributor

@replay replay Feb 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 spaces after the .

@@ -14,14 +14,14 @@ accounting-period = 5min
# see https://github.com/raintank/metrictank/blob/master/docs/data-knobs.md for more details
# duration of raw chunks. e.g. 10min, 30min, 1h, 90min...
chunkspan = 2h
# number of raw chunks to keep in memory. should be at least 1 more than what's needed to satisfy aggregation rules
# number of raw chunks to keep in memory ringbuffer. should be at least 1 more than what's needed to satisfy aggregation rules
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

numchunks has nothing to do with aggregation rules

@Dieterbe Dieterbe merged commit e62b385 into master Feb 24, 2017
@Dieterbe Dieterbe deleted the faq branch January 2, 2018 16:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants